Add tooling for Lens verification#244
Merged
fedgiac merged 3 commits intonew-chain-deploymentsfrom Jul 31, 2025
Merged
Conversation
anxolin
approved these changes
Jul 30, 2025
Contributor
anxolin
left a comment
anxolin
left a comment
There was a problem hiding this comment.
I tested that:
- Addressed match!
- They are verified with EXACT MATCH
- The bytecode matched mainnet (*1)
(*1) For the settlement contract, the bytecode is slightly different for some reason.
I didn't test test the validation itself work, because the command threw an error saying that they were already validated, also --force didn't help, but I trust they were validated using that command :)
| }, | ||
| etherscan: { | ||
| apiKey: { | ||
| lens: "unneeded", |
Contributor
Author
The deployment calldata is exactly the same (otherwise we can't get the same address). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds tooling needed to fully verify a deployment on Lens.
It uses the same verification procedure from 0ae8a26, but it uses the
new-chain-deploymentbranch to guarantee that the metadata matches as well (and so the full verification works, not just the partial one).I took the verification URL from internal discussion with the Lens team.
The commands are:
Note that I added Sourcify verification as well despite Sourcify not supporting Lens. That's more for future tricky deployments since it can turn out to be handy.
I was unable to verify the authenticator itself. That's because it's a proxy and the proxy artifacts aren't available for the script to pick up. In particular, the following command does not work:
Test Plan
Check out the vault relayer, the settlement contract, and the allow list authentication implementation.
Extra chores
GitHub deprecated the action we rely on (1, 2). To fix that I just copied what we do on main.